Packet-based usage tracking for a wireless device

ABSTRACT

A system for tracking usage of a wireless device includes monitoring, at a tracking device connected to and different from a wireless network, information regarding a first data packet sent from a wireless device to the wireless network, wherein the information regarding the first data packet includes an identifier of the wireless device, an identifier of a first type of wireless service, and an amount of data included in the first data packet.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/904,765 filed on Feb. 26, 2018, now U.S. Pat. No. 10,117,077 issuedon Oct. 30, 2018; which is a continuation of U.S. application Ser. No.15/592,743 filed on May 11, 2017, now U.S. Pat. No. 9,906,933 issued onFeb. 27, 2018; which is a continuation of U.S. application Ser. No.14/209,748 filed on Mar. 13, 2014 now U.S. Pat. No. 9,681,283 issued onJun. 13, 2017; which also claims the benefit from U.S. ProvisionalApplication No. 61/782,085 filed on Mar. 14, 2013. These applicationsare hereby incorporated by reference in their entirety for all purposesas if fully set forth herein.

TECHNICAL FIELD

The following disclosure generally relates to tracking usage of awireless device and, more particularly, relates to tracking usage ofvarious services of a wireless device connected to a wireless network bymonitoring data packets of a wireless network.

BACKGROUND

Wireless services, such as cellular or mobile phone services, typicallyinclude voice services, Short Message Service (“SMS”) services, and dataservices. A wireless service provider typically bundles a particularnumber of voice minutes, a particular number of SMS messages, and anamount of data transfer for a prepaid or postpaid monthly wireless plan.A subscriber will purchase a bundle appropriate for his/her usage. Whenthe subscriber places or receives a call, sends or receives an SMSmessage, and/or uploads or downloads data from his/her wireless device,appropriate units of usage are deducted from the subscriber's monthlywireless plan.

In prior wireless networks, the usage of each wireless service could betracked because each type of wireless service was managed by differentswitches. For example, voice calls were routed through circuit switches,SMS messages were routed through SMS centers (“SMSC”), and data wasrouted through various servers. Therefore, by monitoring and/orreceiving feedback from each of the switches, the usage of a particularwireless device could be tracked.

However, emerging wireless networks route all wireless services aspacket data through a single switch or limited number of switches. Forexample, voice calls can be transmitted as data over Long Term Evolution(“LTE”) networks using various protocols, such as Voice over LTE(“VoLTE”). Therefore, voice calls and SMS messages in emerging wirelessnetworks are tracked as data usage, making it difficult to appropriatelydeduct voice minutes and SMS messages from the subscriber's monthlyplan. As such, the current methods of monitoring and/or receivingfeedback from switches of a wireless network cannot be applied toaccurately track usage of a wireless device over an emerging wirelessnetwork.

Therefore, a new method and system for more accurately tracking usage ofa wireless device connected to an emerging wireless network is needed.

SUMMARY

Details of one or more implementations of packet-based usage trackingfor a wireless device are set forth in the accompanying drawings and thedescription below. Other aspects of the packet-based usage tracking fora wireless device will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary wireless device.

FIG. 2 illustrates an exemplary wireless device.

FIG. 3 illustrates a schematic diagram showing the connectivity betweena wireless device, a plurality of mobile network operators, and a mobilevirtual network operator.

FIG. 4 illustrates a schematic block diagram of an exemplary wirelessdevice including software modules for packet-based usage tracking.

FIG. 5 illustrates a schematic block diagram of an exemplary mobilevirtual network operator cloud including software modules forpacket-based usage tracking.

FIG. 6 illustrates an exemplary data packet header structure.

FIG. 7 illustrates an exemplary wireless service identifier databasestructure.

FIG. 8 illustrates another exemplary wireless service identifierdatabase structure.

FIG. 9 illustrates a flowchart showing an exemplary process forpacket-based usage tracking for a wireless device.

Like reference symbols indicate like elements throughout thespecification and drawings.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of an exemplary wireless device. Thewireless device 10 can be any mobile technology computing device thatconnects to a wireless communication network such as, for example, amobile phone, a wireless handset, a wireless dongle, user equipment, amobile station, or the like. The wireless device 10 includes a display12, an input device 14, a transceiver 16, a processor 18, a memory 20,and may include a Universal Integrated Circuit Card (“UICC”) orSubscriber Identity Module (“SIM”) card 22. In some implementations, theSIM card 22 can be removably received within a card slot (not shown) inthe wireless device 10 and can include internal SIM memory 24. The SIMcard 22 can store information such as an International Mobile SubscriberIdentity (“IMSI”), a key used to identify and authenticate subscribersusing the wireless device 10, or the like. The SIM card 22 can beconfigured to be transferred between different wireless devices 10. Inother implementations, the wireless device 10 can operate without a UICCor SIM card 22.

The processor 18 is capable of processing instructions for executionwithin the wireless device 10. For example, the processor 18 can processinstructions stored in the memory 20 to display graphical information onthe display 12 and/or to transmit or receive data using the transceiver16. The processor 18 can be a single-threaded processor or amulti-threaded processor. The memory 20 can include, for example,volatile or non-volatile random access memory (“RAM”) and/or read onlymemory (“ROM”). The components 12, 14, 16, 18, and 20 within thewireless device 10 communicate through an internal bus 26.

FIG. 2 illustrates an exemplary wireless device. The wireless device 10may include a display 12 that is a screen that can be touch sensitive.The input device 14 can include one or more of a keypad 28, a trackball30, selectable buttons 32, a touch screen 34 having selectable regions,or the like. The wireless device 10 may also include an antenna (notshown) coupled to the transceiver 16 to facilitate the transmission andreceipt of communications by the wireless device 10.

FIG. 3 illustrates a schematic diagram showing the connectivity betweena wireless device 10, a plurality of mobile network operators (“MNO”)networks 302 and 304, and a mobile virtual network operator (“MVNO”)cloud 306. Although two MNO networks 302 and 304 are illustrated in FIG.3, any number of MNO networks can be available. The wireless device 10may connect to one of the MNO networks 302 and 304 depending on thegeographic location of the wireless device 10, the availability of theMNO networks 302 and 304, and/or the service contract associated withthe wireless device 10. The MNO networks 302 and 304 can be any type ofwireless network, such as a cellular data network, e.g., a Global Systemfor Mobile Communication (“GSM”) network, a Code-Division MultipleAccess (“CDMA”) network, a Universal Mobile Telecommunications System(“UMTS”) network, an Evolution-Data Optimized (“EV-DO”) network, a LTEnetwork, a wireless local network, a wide area network, and/or the like.

In some implementations, a wireless subscriber purchases a wirelesscommunications plan from a MVNO. The MVNO is a wireless operator thattypically does not own its own frequency spectrum or have its ownnetwork infrastructure. Instead, MVNOs contract for the right to accessa wireless communications network owned by a MNO and sell that access totheir wireless subscribers. Therefore, to provide activation, metering,additional services, and other customer services to their subscribers,MVNOs operate systems, such as the MVNO cloud 306, that communicate withthe MNO networks 302 and 304.

The MVNO cloud 306 may communicate with the MNO networks 302 and 304 toreceive information about the usage of the wireless device 10 on the MNOnetworks 302 and 304. The MVNO cloud 306 can be one or more of dedicatedhardware, application specific integrated circuits, programmable logicarrays, computers, and servers including one or more processors and oneor more memories. For example, the one or more processors of the MVNOcloud 306 can be configured to perform the functions of the trackingmodule 308 and the one or more memories of the MVNO cloud 306 can beconfigured to store the usage information of the subscribers of the MVNOand a wireless service identifier database.

The usage information can include information regarding data packetsreceived at the MNO networks 302 and 304 from the wireless device 10. Insome implementations, the usage information can be the header of eachpacket that is sent between the wireless device 10 and the MNO networks302 and 304, as described in greater detail with regard to FIG. 6. Inother implementations, the usage information can include the number ofdata packets received by the MNO networks 302 and 304 over apredetermined time period, an alphanumeric identifier of the wirelessdevice 10, an alphanumeric identifier of the wireless service using thedata packets, the size of the data packets, time stamps included in thedata packets, and an alphanumeric identifier of the destination of thedata packets. An indicator of the type of wireless service using thedata packets can be included in the header or the body of each datapacket.

To track the usage of the wireless device 10, tracking modules 308and/or 310 are used. In some implementations, the tracking module 308can be included in the MVNO cloud 306. In other implementations, thetracking module 310 can be included in the wireless device 10. In yetother implementations, the tracking modules 308 and 310 can be locatedin both the MVNO cloud 306 and the wireless device 10. For example, thetracking module 310 can add wireless service identifiers to the datapackets sent by and/or received at the wireless device 10 and thetracking module 308 can accumulate the usage of each wireless servicefor each wireless device 10. The usage information can be sent betweenthe tracking modules 308 and 310 through one or more of the MNO networks302 and 304.

The tracking modules 308 and 310 can be implemented as one or more ofsoftware or hardware. The tracking modules 308 and 310 can coordinateone or more of provisioning, metering, accumulating, and consolidatingwireless service usage for the wireless subscribers of the wirelessdevice 10.

The tracking module 310 included in the wireless device 10 may bepre-installed or post-installed on the wireless device 10. The trackingmodule 310 may be stored or executed on, for example, the memory 20, theUICC/SIM memory 24, dedicated hardware, application specific integratedcircuits, programmable logic arrays, and/or the processor 18 of thewireless device 10. The instructions for the tracking module 310 may beincluded in hardware of the wireless device 10 or in an applicationstored in the memory 20 and/or the SIM memory 24 of the wireless device10 and run by the operating system of the wireless device 10.

FIG. 4 illustrates a schematic block diagram of an exemplary wirelessdevice including software modules for packet-based usage tracking. Thewireless device 10 includes at least a communications processing module402 communicating with the transceiver 16, and a tracking module 310including a usage information memory 404 and a wireless serviceidentifier database 406. The tracking module 310, including the wirelessservice identifier database 406, can be pre-configured or post-installedin the wireless device 10 and can be updated over time using Over TheAir (“OTA”) programming or non-OTA programming.

In some implementations, the modules 310 and 402 are one or more ofsoftware, hardware, and firmware implementations that perform orfacilitate the processes, features, and/or functions described withreference to the modules 310 and 402. The processes, features, and/orfunctions of the modules 310 and 402 may be performed with or withouthuman interaction or augmentation.

In some implementations, the modules 310 and 402 may be separatesoftware modules or, in other implementations, the functions performedby the modules 310 and 402 may be performed by a single software module.In some implementations, each of the modules 310 and 402 may includemultiple software modules to perform the processes, features, and/orfunctions of the modules 310 and 402. If the modules 310 and 402 aresoftware modules, they can be stored in the memory 20 and/or the SIMmemory 24 of the wireless device 10 and be executed by the processor 18and/or a processor included on the SIM card 22.

The tracking module 310 may include a wireless service identifierdatabase 406 that associates predefined identifiers, such as multiplebits, with predefined wireless services, as explained in greater detailwith reference to FIGS. 7 and 8. The tracking module 310 also includes ausage information memory 404 that stores the usage informationassociated with a particular wireless subscriber and/or wireless device.The tracking module 310 can store the usage of various wireless servicessuch as, for example, the number of voice calls, the number of freevoice minutes used, the number of metered voice minutes used, the totalnumber of voice minutes used, the number of free SMS messages sentand/or received, the number of metered SMS messages sent and/orreceived, the total number of SMS messages sent and/or received, thefree amount of data uploaded and/or downloaded, the metered amount ofdata uploaded and/or downloaded, and the total amount of data uploadedand/or downloaded. Other types of wireless services are contemplated aswell.

The usage statistics can be stored from the start of a relationshipbetween the wireless subscriber and the MVNO and for predefined timeperiods. For example, the usage statistics can be stored in one monthincrements. The communications processing module 402 can forward theusage information from the usage information memory 404 to the trackingmodule 308 of the MVNO cloud 306 through the MNO networks 302 and 304 atpredetermined time intervals, in response to a request by the MVNO cloud306, in response to a triggering event, or the like. For example, theusage information can be forwarded to the MVNO cloud 306 every threehours, once a day, once a week, in response to movement of the wirelessdevice 10 from a predefined geographic area, in response to each usageof a wireless service, in response to a predefined amount of usage ofone or more wireless services, in response to every startup of thewireless device 10, or the like.

The tracking module 310 also identifies the wireless device 10 and/orthe particular wireless subscriber using the wireless device 10 byproviding identification information of the wireless device 10 and/orthe wireless subscriber. For example, the tracking module 310 caninclude an identification number for the wireless subscriber or anidentification number for the SIM card 22 associated with the wirelesssubscriber, such as an Integrated Circuit Card Identification (“ICCID”),Electronic Serial Number (“ESN”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),Local Area Identity (“LAI”), and/or the like. The identificationinformation can be specific to allow the MVNO to identify the wirelessdevice 10 and/or wireless subscriber. In some implementations, theidentification number for the wireless device 10 can be included in theheader of a data packet.

In some implementations, to avoid compromising the integrity of theidentification information and the usage information, the informationstored on the tracking module 310 can be stored in a secure memory ofthe wireless device 10 and/or encrypted. The identification and usageinformation can be provided to the MVNO cloud 306 in encrypted formand/or according to a specific network protocol.

In some implementations, usage information stored in the tracking module310 can be displayed to the wireless subscriber on the display 12 of thewireless device 10. The usage information can be displayed in responseto a request from the wireless subscriber or at a predetermined time,such as the first day of the month. Current usage information or usageinformation for a previous time period, such as the previous month, canbe displayed.

In some implementations, the wireless service identifier database 406can be a predefined lookup table. In some implementations, the wirelessservice identifier database 406 can be customized for the particularwireless subscriber or the wireless device 10, or be generic for a groupof wireless subscribers. For example, all wireless subscribers of aparticular network operator may have the same wireless serviceidentifier database 406.

FIG. 5 illustrates a schematic block diagram of an exemplary MVNO cloud306 including software modules for packet-based usage tracking. The MVNOcloud 306 includes at least a tracking module 308 including a usageinformation memory 502 and a wireless service identifier database 504.The tracking module 308 can be pre-configured or post-installed in theMVNO cloud 306. The tracking module 308 can receive usage informationfrom the tracking module 310 of the wireless device 10 and/or fromgateways of the MNO networks 302 and 304. The tracking module 308 canreceive the usage information at predetermined time intervals, inresponse to a request by the MVNO cloud 306, in response to a triggeringevent, or the like.

The usage information memory 502 can store the usage information for oneor more of the wireless subscribers of the MVNO. For example, the usageinformation memory 502 can store the usage information for each of thesubscribers of the MVNO. The usage information can be stored from thestart of a relationship between the wireless subscriber and the MVNO andfor predefined time periods. For example, the usage information can bestored in one month increments.

In some implementations, preferably, the wireless service identifierdatabase 504 of the tracking module 308 of the MVNO cloud 306 can be thesame as the wireless service identifier database 406 of the trackingmodule 310 of the wireless device 10. In other implementations, thewireless service identifier database 504 of the tracking module 308 ofthe MVNO cloud 306 can be different from the wireless service identifierdatabase 406 of the tracking module 310 of the wireless device 10. Forexample, the wireless service identifier database 504 can includeidentifiers for all of the types of wireless services, whereas thewireless service identifier database 406 can include identifiers for asubset of the wireless services that are associated with the wirelessdevice 10 or a particular wireless subscriber using the wireless device10. For example, one wireless subscriber may have SMS messagingprivileges, while another wireless subscriber may not.

The functions of the tracking module 308 can be performed by one or moreprocessors of the MVNO cloud 306 and the usage information memory 502and the wireless service identifier database 504 can be stored by one ormore of the memories of the MVNO cloud 306. In some implementations, forexample, the module 308 is one or more of software, hardware, andfirmware implementations that perform or facilitate the processes,features, and/or functions described with reference to the module 308.The processes, features, and/or functions of the module 308 may beperformed with or without human interaction or augmentation.

In some implementations, the module 308 may be separate software modulesor, in other implementations, the functions performed by the module 308may be performed by a single software module. In some implementations,the module 308 may include multiple software modules to perform theprocesses, features, and/or functions of the module 308. If the module308 is a software module, it can be stored in one or more of thememories of the MVNO cloud 306 and be executed by the one or moreprocessors of the MVNO cloud 306.

The tracking module 308 identifies the wireless device 10 and/or theparticular wireless subscriber using the wireless device 10 by receivingidentification information of the wireless device 10 and/or the wirelesssubscriber. The identification information can be included in the headerof a data packet.

In some implementations, to avoid compromising the integrity of theidentification information and the usage information, the informationstored on the tracking module 308 can be stored in a secure memory ofthe MVNO cloud 306 and/or encrypted.

FIG. 6 illustrates an exemplary data packet header structure. The datapacket header 600 can include one or more of the fields 602-630. Aversion identifier field 602 identifies the type of communicationsprotocol. For example, the communications protocol can be an InternetProtocol version 4 (“IPv4”) or an Internet Protocol version 6 (“Ipv6”).The header length field 604 defines the length of the data packet header600. The type of service field 606 can specify a priority for the packetand request a particular route to the destination. The total lengthfield 608 defines the length of the entire data packet including theheader 600 and the data field 630. The identification field 610 is usedto identify fragments of an original data packet. The flags field 612 isused to control or identify fragments. The fragment offset field 614specifies the offset of a particular fragment relative to the beginningof the original unfragmented data packet. The time to live field 616limits a data packet's lifetime in time or hop count. The protocol field618 defines the protocol used in the data field 630 of the data packet.The header checksum field 620 is used for error-checking of the header.

The source address field 622 is an identifier of the source of the datapacket. The source address field 622 can include an internet protocol(“IP”) address for the source or another identifier of the source. Thesource address field 622 can identify the wireless device 10 or aparticular subscriber using the wireless device 10. The destinationaddress field 624 is an identifier of the destination of the datapacket. The destination address field 624 can include an IP address forthe destination or another identifier of the destination. Thedestination address field 624 can identify one of the MNO networks 302and 304, an identifier of a contact that the wireless device 10 isrequesting to contact, or an identifier of a server that the wirelessdevice 10 is requesting to contact.

The options field 626 is an optional field that supports variousoptions, such as security, routing, and error reporting. In someimplementations, an identifier of a type of wireless service can beincluded in the options field 626 of a data packet. The padding field628 includes additional bits so that the data packet header 600 ends ona particular bit boundary. The data field 630 is appended to the datapacket header 600 to complete the data packet. The data field 630includes the data being sent to and from the wireless device 10. In someimplementations, an identifier of a type of wireless service can beincluded in the data field 630 of a data packet. In someimplementations, a time stamp can also be included in the data field 630of a data packet.

In some implementations, depending on the communications protocoladopted by the MNO networks 302 and 304 or the MVNO cloud 306 and/or thetype of wireless network that the wireless device 10 connects to, theheader 600 of the data packet can differ. For example, one or more ofthe fields 602-628 may not be included or one or more additional fieldsmay be included in headers of other communications protocols. Therefore,the identifier of a type of wireless service can be included in otherfields of the headers for other communications protocols.

FIG. 7 illustrates an exemplary wireless service identifier databasestructure. The database structure 700 includes two-bit wireless serviceidentifiers. In particular, the database structure 700 includes a firstbit field 702 (“Bit 0”), a second bit field 704 (“Bit 1”), and awireless service type field 706. The two-bit wireless serviceidentifiers can be included by the tracking module 310 in the header 600or in the data field 630. For example, in some implementations, thetwo-bit wireless service identifiers can be included in the optionsfield 626, the source address field 622, or the destination addressfield 624. In other implementations, the two-bit wireless serviceidentifiers can be included in one or more of the data packet headerfields 602-628. In yet other implementations, the two-bit wirelessservice identifiers can be included as the first bits in the data field630.

Entry 708 associates a first bit of “0” and a second bit of “0,”combining to a numeric value of “0,” to no type of wireless service. Thetwo-bit identifier 708 may be used for data packets that are notassociated with a wireless service, i.e., for data packets that are notassociated with voice calls, SMS messaging, data requests, or the like.For example, the two-bit identifier 708 can be used in data packets forreceiving software updates from the MVNO cloud 306 or for sending orreceiving usage information from the MVNO cloud 306.

Entry 710 associates a first bit of “0” and a second bit of “1,”combining to a numeric value of “1,” to voice calls. Entry 712associates a first bit of “1” and a second bit of “0,” combining to anumeric value of “2,” to SMS messaging. Finally, entry 714 associates afirst bit of “1” and a second bit of “1,” combining to a numeric valueof “3,” to data services.

The two-bit identifiers shown in FIG. 7 are exemplary and any two-bitidentifiers can be associated with the different types of wirelessservices. For example, in some implementations, the first bit of “0” andthe second bit of “1” can be associated with SMS messaging rather thanvoice calls.

The wireless service type field 706 includes alphanumeric identifiers ofthe type of wireless service. For example, no service 708 can beidentified by “NON,” voice service 710 can be identified by “VOC,” SMSmessaging service 712 can be identified by “SMS,” and data service 714can be identified by “DAT.” The alphanumeric identifiers of FIG. 7 areexemplary, however, and identifiers of any length including letters,numbers, and/or symbols can be used.

FIG. 8 illustrates another exemplary wireless service identifierdatabase structure. The database structure 800 includes three-bitwireless service identifiers. In particular, the database structure 800includes a first bit field 802 (“Bit 0”), a second bit field 804 (“Bit1”), a third bit field 806 (“Bit 2”), and a wireless service type field808. The three-bit wireless service identifiers can be included by thetracking module 310 in the header 600 or in the data field 630. Forexample, in some implementations, the three-bit wireless serviceidentifiers can be included in the options field 626, the source addressfield 622, or the destination address field 624. In otherimplementations, the three-bit wireless service identifiers can beincluded in one or more of the data packet header fields 602-628. In yetother implementations, the three-bit wireless service identifiers can beincluded as the first bits in the data field 630.

Entry 810 associates a first bit of “0,” a second bit of “0,” a thirdbit of “0,” combining to a numeric value of “0,” to no type of wirelessservice. Entry 812 associates a first bit of “0,” a second bit of “0,”and a third bit of “1,” combining to a numeric value of “1,” to meteredvoice calls. Entry 814 associates a first bit of “0,” a second bit of“1,” and a third bit of “0,” combining to a numeric value of “2,” tofree voice calls. Free voice calls can be voice calls that are notcounted against the wireless subscriber's usage. For example, callsduring off-peak hours, calls to the MVNO, calls to friends and family,and the like, can be free voice calls.

Entry 816 associates a first bit of “0,” a second bit of “1,” and athird bit of “1,” combining to a numeric value of “3,” to metered SMSmessaging. Entry 818 associates a first bit of “1,” a second bit of “0,”and a third bit of “0,” combining to a numeric value of “4,” to free SMSmessaging. Entry 820 associates a first bit of “1,” a second bit of “0,”and a third bit of “1,” combining to a numeric value of “5,” to metereddata usage. Entry 822 associates a first bit of “1,” a second bit of“1,” and a third bit of “0,” combining to a numeric value of “6,” tofree data usage. Finally, entry 824 associates a first bit of “1,” asecond bit of “1,” and a third bit of “1,” combining to a numeric valueof “7,” to another wireless service. The another wireless service can beany type of wireless selected by the MVNO.

The three-bit identifiers shown in FIG. 8 are exemplary and anythree-bit identifiers can be associated with the different types ofwireless services. For example, in some implementations, the first bitof “0,” the second bit of “1,” and the third bit of “0” can beassociated with free SMS messaging rather than free voice calls.Moreover, although two-bit identifiers are shown in FIG. 7 and three-bitidentifiers are shown in FIG. 8, any number of bits can be used asidentifiers of wireless services. For example, if the MVNO requiresidentification of 16 different types of wireless services, a databasestructure including four-bit wireless service identifiers can beimplemented.

The wireless service type field 808 includes alphanumeric identifiers ofthe type of wireless service. For example, no service 810 can beidentified by “NONE,” metered voice service 812 can be identified by“MVOC,” free voice service 814 can be identified by “FVOC,” metered SMSmessaging service 816 can be identified by “MSMS,” free SMS messagingservice 818 can be identified by “FSMS,” metered data service 820 can beidentified by “MDAT,” free data service 822 can be identified by “FDAT,”and another type of wireless service 824 can be identified by “SERV.”The alphanumeric identifiers of FIG. 8 are exemplary, however, andidentifiers of any length including letters, numbers, and/or symbols canbe used.

FIG. 9 illustrates a flowchart showing an exemplary process forpacket-based usage tracking for a wireless device. One or more steps inthe process 900 can be carried out by, for example, an electronic systemsuch as the wireless device 10, a gateway of the MNO networks 302 and304, and/or the MVNO cloud 306.

Initially, an indicator of a wireless service is inserted in a datapacket associated with the wireless service (step 902). In someimplementations, the tracking module 310 of the wireless device 10and/or the gateway of the MNO networks 302 and 304 can insert thewireless service indicators to the data packets. For example, if aninbound call is received at the wireless device 10, the tracking module310 can include a voice call indicator 710, 812, or 814 to the header600 or data field 630 of the data packets including the voice data. Inanother example, if the user of the wireless device is requesting tosend an SMS message, the tracking module 310 can include an SMSmessaging indicator 712, 816, or 818 to the header 600 or data field 630of the data packets including the SMS messaging data. In yet anotherexample, if an application running on the wireless device 10 requestsdata from a server, the tracking module 310 can include a data indicator714, 820, or 822 to the header 600 or data field 630 of the data packetsincluding the data.

Information regarding the data packets associated with the variouswireless services received at or sent from the wireless device 10 aremonitored by the tracking module 310 of the wireless device, the gatewayof the MNO networks 302 and 304, and/or the MVNO cloud 306 (step 904).In some implementations, the information regarding the data packets caninclude one or more of an identifier of the wireless device 10 or awireless subscriber using the wireless device 10, an identifier of thetype of wireless service, a number of data packets, an amount of dataincluded in the data packets associated with the wireless service, andthe time stamps of the data packets. In other implementations, theinformation regarding the data packets can include the entire header 600of each data packet. In yet other implementations, the informationregarding the data packets can include the entire data packet includingthe entire header 600 and entire data field 630 of each data packet.

In some implementations, the information regarding the data packetsassociated with the various wireless services received at or sent fromthe wireless device 10 can be monitored following the end of acommunication. For example, the information regarding the data packetsassociated with a voice call can be monitored following completion ofthe voice call. In another example, the information regarding the datapackets associated with an SMS message can be monitored followingreception of the SMS message. Therefore, if the communication associatedwith the various wireless services includes multiple data packets, theinformation regarding all of the data packets associated with thatcommunication can be monitored at the end of the communication.

In other implementations, the information regarding the data packetsassociated with the various wireless services received at or sent fromthe wireless device 10 can be monitored following transmission of eachdata packet. For example, if a voice call requires the transmission ofmultiple data packets, information regarding each data packet can bemonitored following transmission of each data packet.

In some implementations, the information regarding the data packetsassociated with the various wireless services received at or sent fromthe wireless device 10 can be sent from, for example, the trackingmodule 310 of the wireless device 10 or the gateway of the MNO networks302 and 304 to the tracking module 308 of the MVNO cloud 306. In otherimplementations, the tracking module 308 of the MVNO cloud 306 canmonitor one or more ports of one or more gateways of the MNO networks302 and 304 to receive the information regarding the data packetsassociated with the various wireless services received at or sent fromthe wireless device 10.

The usage of each wireless service for the wireless device 10 isdetermined based on the monitored information regarding the data packets(step 906). The tracking module 310 of the wireless device 10, thegateway of the MNO networks 302 and 304, or the tracking module 308 ofthe MVNO cloud 306 can determine the usage of each wireless service. Insome implementations, the tracking module 310 of the wireless device 10or the gateway of the MNO networks 302 and 304 can determine the usageof each wireless service and forward the usage information to thetracking module 308 of the MVNO cloud 306. In other implementations, thetracking module 308 of the MVNO cloud 306 can receive the informationregarding the data packets and determine the usage of each wirelessservice for each wireless device 10.

The multi-bit identifier of the wireless service is compared to thewireless service identifier database 406 and 504 to determine the typeof wireless service associated with one or more data packets includingthat multi-bit identifier. The total units of usage for eachcommunication are associated to the corresponding wireless service andwireless device 10. The amount of data associated with each data packetcan be determined by, for example, subtracting the header length field604 from the total length field 608.

In some implementations, the amount of data associated with each usageof a wireless service can be summed to determine the total usage of thatwireless service. For example, the total amount of data transmitted inthe data field 630 of each data packet including a data serviceidentifier can be summed to determine data service usage. In anotherexample, the number of data packets including an SMS messaging serviceindicator can be summed to determine the number of SMS messages used. Inyet another example, the amount of data transmitted in the data field630 of each data packet including an SMS messaging service indicator canbe divided by a predetermined amount of data per SMS message todetermine the number of SMS messages used.

With regard to the usage of voice service, if the MNO networks 302 and304 use a fixed amount of data for every unit of voice usage, then theunits of voice usage can be determined by dividing the total amount ofdata transmitted in the data field 630 of each data packet including avoice service indicator by the fixed amount of data per unit of voiceusage. For example, if 384 kb of data is transferred for a single voicecall and the MNO networks 302 and 304 send and receive voice data at 12kb/s, then 32 seconds of voice usage is determined for the wirelessdevice 10.

However, if the MNO networks 302 and 304 use a variable amount of datafor every unit of voice usage, then the units of voice usage can bedetermined based on the time stamps of the data packets. For example, ifthe first data packet for a voice communication is transmitted at 9:14AM and the final data packet for the voice communication is transmittedat 9:25 AM, then 11 minutes of voice usage for the wireless device 10 isdetermined.

The usages for the wireless services are then accumulated for eachwireless device at the MVNO cloud 306 based on the determined usage ofeach wireless service (step 908). For example, the usage of eachcommunication of a wireless service determined in step 906 can be summedtogether for each type of wireless service. In particular, if thewireless device 10 uses three voice communications of, for example, fiveminutes, eight minutes, and ten minutes over a predetermined timeperiod, 23 minutes of voice service is accumulated for the particularwireless device 10. In another example, if the wireless device 10 usesone free voice communication of five minutes and two metered voicecommunications of eight minutes and ten minutes, then 18 minutes ofvoice service is accumulated for the particular wireless device 10.

Similarly, the total number of SMS messages or the metered number of SMSmessages can be accumulated and/or the total amount of data or themetered amount of data can be accumulated for the particular wirelessdevice 10.

The total usage of the wireless services for each wireless device 10 arestored (step 910). In some implementations, the total usage of thewireless services can be stored in the usage information memory 502 ofthe tracking module 308 of the MVNO cloud 306. For example, for eachwireless device 10, the usage information memory 502 can store, forexample, the number of voice calls, the number of free voice minutesused, the number of metered voice minutes used, the total number ofvoice minutes used, the number of free SMS messages sent and/orreceived, the number of metered SMS messages sent and/or received, thetotal number of SMS messages sent and/or received, the free amount ofdata uploaded and/or downloaded, the metered amount of data uploadedand/or downloaded, and the total amount of data uploaded and/ordownloaded. The total usages can be stored from the start of arelationship between a wireless subscriber and/or the MVNO and forpredefined time periods. For example, the total usage statistics can bestored in one month increments.

It is to be understood that the implementations are not limited toparticular systems or processes described which may, of course, vary. Itis also to be understood that the terminology used herein is for thepurpose of describing particular implementations only, and is notintended to be limiting. As used in this specification, the singularforms “a,” “an,” and “the” include plural referents unless the contentclearly indicates otherwise. Thus, for example, reference to “a wirelessdevice 10” includes two or more wireless devices.

Reference to “one implementation,” “some implementations,” “otherimplementations,” or “one or more implementations” means that aparticular feature, structure, or characteristic described in connectionwith the implementation is included in at least one implementation butnot necessarily in the same implementation or separate implementationsthat are mutually exclusive. Moreover, various features may be exhibitedby some implementations and not by other implementations. Similarly,various requirements are described that may be requirements for someimplementations but not other implementations.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the claims. For example, the wirelessdevice 10 may not utilize a UICC or SIM card 22. The wireless device 10may operate using any mobile operating system.

Although for the sake of clarity and simplicity, exemplaryimplementations of the invention is described in terms of a wirelessdevice 10 used in a MVNO communications system, it should be understoodthat the invention is not limited to these exemplary implementations.Alternative implementations of the invention may include any wirelessdevice with internally stored rules of operation that may be changedtogether with other mobile communications devices within a select groupvia a broadcast message received from the MVNO. Accordingly, otherimplementations are within the scope of this application.

In an embodiment, the invention may be implemented in any type of mobilesmartphones that are operated by any type of advanced mobile dataprocessing and communication operating system, such as, e.g., an Apple™iOS™ operating system, a Google™ Android™ operating system, a RIM™Blackberry™ operating system, a Nokia™ Symbian™ operating system, aMicrosoft™ Windows Mobile™ operating system, a Microsoft™ Windows Phone™operating system, a Linux™ operating system or the like.

Further in accordance with various embodiments of the invention, themethods described herein are intended for operation with dedicatedhardware implementations including, but not limited to, PCs, PDAs,semiconductors, application specific integrated circuits (ASIC),programmable logic arrays, cloud computing devices, and other hardwaredevices constructed to implement the methods described herein.

It should also be noted that the software implementations of theinvention as described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium such as a disk or tape; amagneto-optical or optical medium such as a disk; or a solid statemedium such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories. A digital file attachment to email orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the invention is considered to include a tangiblestorage medium or distribution medium, as listed herein and includingart-recognized equivalents and successor media, in which the softwareimplementations herein are stored.

The many features and advantages of the invention are apparent from thedetailed specification, and, thus, it is intended by the appended claimsto cover all such features and advantages of the invention which fallwithin the true spirit and scope of the invention. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the invention to theexact construction and operation illustrated and described, and,accordingly, all suitable modifications and equivalents may be resortedto that fall within the scope of the invention.

What is claimed is:
 1. A system configured to track wireless serviceusage of a wireless device, comprising: a tracking processor configuredto be implemented in at least one of the following: a mobile networkoperator system, a mobile virtual network operator system, and thewireless device; the tracking processor further configured to monitortransmission in a wireless network of a first data packet and a seconddata packet and insert an identifier of a first type of wireless serviceinto the first data packet and the second data packet, the first datapacket and the second data packet being associated with wireless servicein the wireless network used by the wireless device; the trackingprocessor further configured to monitor information regarding the firstdata packet, wherein the information regarding the first data packetincludes an identifier of the wireless device, the identifier of thefirst type of wireless service, and an amount of data for the first typeof wireless service; the tracking processor further configured todetermine a first usage of the first type of wireless service based onthe information regarding the first data packet; the tracking processorfurther configured to store in a memory the first usage of the firsttype of wireless service for the wireless device; the tracking processorfurther configured to monitor information regarding the second datapacket, wherein the information regarding the second data packetincludes the identifier of the wireless device, the identifier of thefirst type of wireless service, and the amount of data for the firsttype of wireless service; the tracking processor further configured todetermine second usage of the first type of wireless service based onthe information regarding the second data packet; the tracking processorfurther configured to store in the memory the second usage of the firsttype of wireless service for the wireless device; the tracking processorfurther configured to accumulate in the memory the first usage of thefirst type of wireless service and the second usage of the first type ofwireless service as a total usage of the first type of wireless servicefor the wireless device; and the tracking processor further configuredto store in the memory the total usage of the first type of wirelessservice for the wireless device, wherein the identifier of the firsttype of wireless service is included in the first data packet and thesecond data packet.
 2. The system of claim 1, wherein: the trackingprocessor is further configured to monitor information regarding a thirddata packet, wherein the information regarding the third data packetincludes the identifier of the wireless device, an identifier of asecond type of wireless service, and an amount of data for the secondtype of wireless service; the tracking processor is further configuredto determine a first usage of the second type of wireless service basedon the information regarding the third data packet; and the trackingprocessor is further configured to store in the memory the first usageof the second type of wireless service for the wireless device, wherein:the second type of wireless service is different from the first type ofwireless service, and the identifier of the second type of wirelessservice is included in the third data packet.
 3. The system of claim 1,wherein the tracking processor is further configured to insert theidentifier based on a type of wireless service.
 4. The system of claim1, wherein the tracking processor is further configured to store in thememory the total usage of the first type of wireless service for thewireless device.
 5. The system of claim 1, wherein the identifier of thefirst type of wireless service comprises two or more bits.
 6. The systemof claim 1, wherein the identifier of the first type of wireless serviceis included in a header of the first data packet and in a header of thesecond data packet.
 7. The system of claim 1, wherein the identifier ofthe first type of wireless service is included in a data field of thefirst data packet and in a data field of the second data packet.
 8. Thesystem of claim 1, wherein the tracking processor is implemented outsidethe wireless device.
 9. The system of claim 1, wherein the trackingprocessor is further configured to compare the identifier of the firsttype of wireless service to a wireless service identifier database. 10.The system of claim 9, wherein the wireless service identifier databasecomprises a lookup table including a two or more bit fields and awireless service type field.
 11. The system of claim 1, wherein thefirst type of wireless service is selected from the group consisting ofvoice service, Short Message Service messaging service, and dataservice.
 12. The system of claim 11, wherein the total usage of thefirst type of wireless service is selected from the group consisting ofa number of voice minutes, a number of Short Message Service messages,and an amount of data.
 13. The system of claim 1, wherein the trackingprocessor is further configured to monitor the information regarding thefirst data packet sent from the wireless device to the wireless networkfollowing an end of communication of the first type of wireless servicefrom the wireless device to the wireless network.
 14. The system ofclaim 1, wherein the tracking processor is further configured to monitorthe information regarding the first data packet sent from the wirelessdevice to the wireless network following transmission of the first datapacket from the wireless device to the wireless network.
 15. The systemof claim 1, wherein the tracking processor is further configured todetermine the first usage of the first type of wireless service based onthe amount of data included in the first data packet.
 16. The system ofclaim 1, wherein the wireless device includes a mobile phone.
 17. Asystem configured to track wireless service usage of a wireless device,comprising: a tracking processor configured to be implemented in atleast one of the following: a mobile network operator system, a mobilevirtual network operator system, and the wireless device; the trackingprocessor further configured to monitor transmission in a wirelessnetwork of a first data packet and a second data packet and insert anidentifier of a first type of wireless service into the first datapacket and the second data packet, the first data packet and the seconddata packet being associated with wireless service in the wirelessnetwork for the wireless device; the tracking processor furtherconfigured to monitor information regarding the first data packet,wherein the information regarding the first data packet includes anidentifier of the wireless device, the identifier of the first type ofwireless service, and an amount of data for the first type of wirelessservice; the tracking processor further configured to determine a firstusage of the first type of wireless service based on the informationregarding the first data packet; the tracking processor furtherconfigured to store in a memory the first usage of the first type ofwireless service for the wireless device; the tracking processor furtherconfigured to monitor information regarding the second data packet,wherein the information regarding the second data packet includes theidentifier of the wireless device, the identifier of the first type ofwireless service, and the amount of data for the first type of wirelessservice; the tracking processor further configured to determine secondusage of the first type of wireless service based on the informationregarding the second data packet; the tracking processor furtherconfigured to store in the memory the second usage of the first type ofwireless service for the wireless device; the tracking processor furtherconfigured to accumulate in the memory the first usage of the first typeof wireless service and the second usage of the first type of wirelessservice as a total usage of the first type of wireless service for thewireless device; and the tracking processor further configured to storein the memory the total usage of the first type of wireless service forthe wireless device, wherein the identifier of the first type ofwireless service is included in the first data packet and the seconddata packet.
 18. The system of claim 17, wherein: the tracking processoris further configured to monitor information regarding a third datapacket, wherein the information regarding the third data packet includesthe identifier of the wireless device, an identifier of a second type ofwireless service, and an amount of data for the second type of wirelessservice; the tracking processor is further configured to determine afirst usage of the second type of wireless service based on theinformation regarding the third data packet; and the tracking processoris further configured to store the first usage of the second type ofwireless service for the wireless device, wherein: the second type ofwireless service is different from the first type of wireless service,and the identifier of the second type of wireless service is included inthe third data packet.
 19. The system of claim 17, wherein the trackingprocessor is further configured to insert the identifier based on a typeof wireless service.
 20. The system of claim 17, wherein the trackingprocessor is further configured to store the total usage of the firsttype of wireless service for the wireless device.